-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[deps]: Update gh minor #184
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/gh-minor
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+14
−14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bitwarden-bot
changed the title
[deps]: Update gh minor
[PM-14690] [deps]: Update gh minor
Nov 11, 2024
Internal tracking:
|
renovate
bot
changed the title
[PM-14690] [deps]: Update gh minor
[deps]: Update gh minor
Nov 11, 2024
vgrassia
previously approved these changes
Nov 11, 2024
renovate
bot
force-pushed
the
renovate/gh-minor
branch
2 times, most recently
from
November 12, 2024 21:12
c7f5cd4
to
8d2a9bf
Compare
KatherineInCode
previously approved these changes
Nov 13, 2024
New Issues
|
🤔 @vvolkgang @vgrassia it looks like the tests are failing because renovate doesn't have appropriate permissions. Is there a way we can run tests as one of us to get around that? Or give renovate those permissions? |
renovate
bot
force-pushed
the
renovate/gh-minor
branch
3 times, most recently
from
November 20, 2024 17:04
48d79c8
to
d9efa4b
Compare
KatherineInCode
previously approved these changes
Nov 21, 2024
renovate
bot
force-pushed
the
renovate/gh-minor
branch
from
November 25, 2024 09:24
d9efa4b
to
b0e4709
Compare
renovate
bot
force-pushed
the
renovate/gh-minor
branch
4 times, most recently
from
December 7, 2024 01:37
5dabc22
to
1d922c1
Compare
renovate
bot
force-pushed
the
renovate/gh-minor
branch
6 times, most recently
from
December 17, 2024 12:09
dd2ba54
to
d48cb78
Compare
renovate
bot
force-pushed
the
renovate/gh-minor
branch
from
December 17, 2024 23:32
d48cb78
to
85b3511
Compare
renovate
bot
force-pushed
the
renovate/gh-minor
branch
from
December 20, 2024 21:17
85b3511
to
f0cae44
Compare
renovate
bot
force-pushed
the
renovate/gh-minor
branch
from
December 23, 2024 20:03
f0cae44
to
c558c98
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v4.1.2
->v4.2.0
v1.11.0
->v1.11.1
v4.4.3
->v4.5.0
2.0.36
->2.0.40
v2.3.0
->v2.5.0
v3.27.0
->v3.28.0
v1.197.0
->v1.205.0
Release Notes
actions/cache (actions/cache)
v4.2.0
Compare Source
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version
v4
orv3
as soon as possible before February 1st, 2025. (Upgrade instructions below).If you are using pinned SHAs, please use the SHAs of versions
v4.2.0
orv3.4.0
If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Read more about the change & access the migration guide: reference to the announcement.
Minor changes
Minor and patch version updates for these dependencies:
1.11.1
1.1.3
0.38.3
Full Changelog: actions/cache@v4...v4.2.0
actions/create-github-app-token (actions/create-github-app-token)
v1.11.1
Compare Source
What's Changed
Bug Fixes
Full Changelog: actions/create-github-app-token@v1.11.0...v1.11.1
actions/upload-artifact (actions/upload-artifact)
v4.5.0
Compare Source
checkmarx/ast-github-action (checkmarx/ast-github-action)
v2.0.40
Compare Source
What's Changed
Other Changes
Full Changelog: Checkmarx/ast-github-action@2.0.39...2.0.40
v2.0.39
Compare Source
What's Changed
Other Changes
Full Changelog: Checkmarx/ast-github-action@2.0.38...2.0.39
v2.0.38
Compare Source
What's Changed
Other Changes
New Contributors
Full Changelog: Checkmarx/ast-github-action@2.0.37...2.0.38
v2.0.37
Compare Source
What's Changed
Other Changes
Full Changelog: Checkmarx/ast-github-action@2.0.36...2.0.37
crowdin/github-action (crowdin/github-action)
v2.5.0
Compare Source
What's Changed
Full Changelog: crowdin/github-action@v2.4.0...v2.5.0
v2.4.0
Compare Source
What's Changed
Full Changelog: crowdin/github-action@v2.3.0...v2.4.0
github/codeql-action (github/codeql-action)
v3.28.0
Compare Source
v3.27.9
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2
andv3
of the CodeQL Action is the node version they support, withv3
running on node 20 while we continue to releasev2
to support running on node 16. For example3.22.11
was the firstv3
release and is functionally identical to2.22.11
. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.3.27.9 - 12 Dec 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v3.27.8
Compare Source
v3.27.7
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2
andv3
of the CodeQL Action is the node version they support, withv3
running on node 20 while we continue to releasev2
to support running on node 16. For example3.22.11
was the firstv3
release and is functionally identical to2.22.11
. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.3.27.7 - 10 Dec 2024
See the full CHANGELOG.md for more information.
v3.27.6
Compare Source
v3.27.5
Compare Source
v3.27.4
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2
andv3
of the CodeQL Action is the node version they support, withv3
running on node 20 while we continue to releasev2
to support running on node 16. For example3.22.11
was the firstv3
release and is functionally identical to2.22.11
. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.3.27.4 - 14 Nov 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v3.27.3
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2
andv3
of the CodeQL Action is the node version they support, withv3
running on node 20 while we continue to releasev2
to support running on node 16. For example3.22.11
was the firstv3
release and is functionally identical to2.22.11
. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.3.27.3 - 12 Nov 2024
No user facing changes.
See the full CHANGELOG.md for more information.
v3.27.2
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2
andv3
of the CodeQL Action is the node version they support, withv3
running on node 20 while we continue to releasev2
to support running on node 16. For example3.22.11
was the firstv3
release and is functionally identical to2.22.11
. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.3.27.2 - 12 Nov 2024
See the full CHANGELOG.md for more information.
v3.27.1
Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
Note that the only difference between
v2
andv3
of the CodeQL Action is the node version they support, withv3
running on node 20 while we continue to releasev2
to support running on node 16. For example3.22.11
was the firstv3
release and is functionally identical to2.22.11
. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.3.27.1 - 08 Nov 2024
See the full CHANGELOG.md for more information.
ruby/setup-ruby (ruby/setup-ruby)
v1.205.0
Compare Source
v1.204.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.203.0...v1.204.0
v1.203.0
Compare Source
Full Changelog: ruby/setup-ruby@v1.202.0...v1.203.0
v1.202.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.201.0...v1.202.0
v1.201.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.200.0...v1.201.0
v1.200.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.199.0...v1.200.0
v1.199.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.198.0...v1.199.0
v1.198.0
Compare Source
What's Changed
Full Changelog: ruby/setup-ruby@v1.197.0...v1.198.0
Configuration
📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.